A breakpoint suspends script execution and transfers control of the script to the debugger. When a breakpoint is encountered, execution is suspended just prior to the breakpoint, and the script execution pointer is positioned at the breakpoint location.
Breakpoints are often used in order to run scripts and stop them just prior to a statement or statements that are to be debugged. Once the script has stopped at a breakpoint, it may be stepped through manually or by using the auto-step feature.
To set a breakpoint in the debugger, click the dash in the narrow column on the left side of the script source code pane. The new break point will be indicated by a small diamond at the break location.
Once a breakpoint has been set, the script can be executed using the Run Script button. Script execution will pause when the breakpoint is reached, as indicated by a highlighted breakpoint and execution pointer arrow. The message pane of the debugger will also indicate that a break point has been reached.
Breakpoints which have been placed in a looping statement will cause the script to stop each time the breakpoint is encountered. When used in conjunction with the Run Script or Auto-Step buttons, such breakpoints can be used to observe conditions occurring within a loop during execution.
Care should be exercised when placing breakpoints within branching statements such as IF..THEN or CASE statements. If the breakpoint is in a branch outside the path of execution, the script will continue to execute.
To clear a breakpoint in the debugger, click the diamond indicating the breakpoint location while script execution is stopped or paused. The breakpoint is removed from the script.